The main parts of a system are Input, Process, Output. However, hardware also needs backing storage as there is no permanent storage in the CPU:
Layers of software have also been implemented, so no direct contact with hardware is necessary:
1.3.2 Identify the data that needs to be held and processed by a system
One of the important processes identified in software development (see section 1.2.2.) was analysis and fact finding. This involves carefully identifying the data which needs to be held and processed by a system. Different systems will require different data to be inputted into it.
1.3.3 Outline suitable means of data capture and output presentation of a system
Data Capture and Output Presentation
Data Capture
Manual Data Entry - Keyboard, mouse
Direct Data Entry - OCR/OMR scanners, barcode scanner etc
Automatic Data Entry - Sensor
Data Presentation
Temporary Displays - VDU, LCD Display
Permanent Display - Printer
Electrical/Mechanical Output - Actuator
1.3.4 Design appropriate data structures to store data within a system
Data in a System When data is in a system it is often shown in flow diagrams with the following symbols:
1.3.5 State the hardware components that are appropriate for a system
A selection of some of the many hardware components appropriate for a system.
Keyboard
Mouse
Monitor
Speakers
Microphone
Always remember that different systems might require different hardware.
1.3.6 Outline a suitable interface between a system and users
The major two user interfaces are Command Line Interfaces (CLI) and Graphical User Interfaces (GUI). CLI's are much easier to implement and use less memory, however, there is a much greater learning curve - yet long term users may find them quicker than other interfaces. GUI's are much more complex to implement and use more memory, they also require a mouse. Yet, icons make it easier to remember commands and these are grouped in menus. There is a much smaller learning curve. GUI's can also be referred to as 'WIMP' (Windows, Icons, Menus, Pointers).
1.3.7 Analyse a systems flowchart that represents a complete system.
1.3.8 Construct a systems flowchart to represent a complete system.
Best content in StJulians_ComputerScience | Diigo - Groups
1.3.1 State the parts of a system
The main parts of a system are Input, Process, Output.
However, hardware also needs backing storage as there is no permanent storage in the CPU:
Layers of software have also been implemented, so no direct contact with hardware is necessary:
1.3.2 Identify the data that needs to be held and processed by a system
One of the important processes identified in software development (see section 1.2.2.) was analysis and fact finding. This involves carefully identifying the data which needs to be held and processed by a system. Different systems will require different data to be inputted into it.
1.3.3 Outline suitable means of data capture and output presentation of a system
Data Capture and Output Presentation
1.3.4 Design appropriate data structures to store data within a system
Data in a System
When data is in a system it is often shown in flow diagrams with the following symbols:
1.3.5 State the hardware components that are appropriate for a system
A selection of some of the many hardware components appropriate for a system.
Always remember that different systems might require different hardware.
1.3.6 Outline a suitable interface between a system and users
The major two user interfaces are Command Line Interfaces (CLI) and Graphical User Interfaces (GUI). CLI's are much easier to implement and use less memory, however, there is a much greater learning curve - yet long term users may find them quicker than other interfaces. GUI's are much more complex to implement and use more memory, they also require a mouse. Yet, icons make it easier to remember commands and these are grouped in menus. There is a much smaller learning curve. GUI's can also be referred to as 'WIMP' (Windows, Icons, Menus, Pointers).
1.3.7 Analyse a systems flowchart that represents a complete system.
1.3.8 Construct a systems flowchart to represent a complete system.
Best content in StJulians_ComputerScience | Diigo - Groups